Elliot,

Can you update your commit message to provide a brief description of what the commit is before? This guide from the Erlang folks is a good summary of how to structure a useful commit message.

"A List Apart" has a slightly longer article that says pretty much the same thing.

My bad, I figured since I had discussed this with Gagan I wouldn't need to explain as much.
I wrote a script to automatically switch to a backup server if the main server goes down, and Gagan wanted to include it in the main website repo, so I added it as a submodule.

@betaredex Instead of copying config.py_SAMPLE to config.py, I think it can be imported directly in switch_host.py as "import config.py_SAMPLE as cfg".

Also, we will have to follow the naming convention and rename config.py_SAMPLE as switch_config.py. And then we need to add the line *config.py to the .gitignore file to avoid uploading it accidentally.

@larsks I know you don't want to be involved in the website development :) But can you please give your opinion on this?

@betaredex Instead of copying config.py_SAMPLE to config.py, I think it can be imported directly in switch_host.py as "import config.py_SAMPLE as cfg".

@gagansk ,

(a) I don't understand the context for your comment, because the files you are discussing are not part of this pull request, and

(b) That's not valid syntax (you import modules, not files, so if you had a file named config_SAMPLE.py you could import config_SAMPLE, but you can't import config.py_SAMPLE unless you have a directory named config containing the files __init__.py and py_SAMPLE.py).

(c) Without seeing the code involved I'm just making stuff up, but it sounds like a bad idea to try importing something with "sample" or "example' in the name (because it's not really a sample, then, it's actual configuration that you're using).